Ticket Management
OBJECTIVE
The Ticket Management option is used to import receivable tickets and to check and correct these tickets. This option is also used to enter a ticket manually.
PREREQUISITES
- Project Management
- Catalogue Management
- Customer Management
- Supplier Management
- Zone Management
- Define Trucks
- Configuration
Icons
Summary
Steps
maestro* > Tickets > Concrete Tickets > Processing > Ticket Management |
Import tickets
- Configure the default manufacturer and file location.
The default manufacturer can be specified in Configuration or, if a source configuration is required, in the project, in Project Management.
- Click the Tools icon and select Import.
Field
Description
Source*
Source of the tickets.
NOTES: If the invoicing project configured in Configuration contains "X" characters, they are replaced by the value imported into the Source field used as a mask, if applicable.
Selection of the source depends on the project type or the first letter of the invoicing project configured in Configuration.
Manufacturer*
Developer of the software that generated the import file. This value is displayed automatically based on the value configured in Project Management and Configuration.
NOTE: The technical specifications for each of the developers is included in the APPENDIX.
Filename*
Location of the file to be imported. A default value can be configured in Project Management and Configuration.
Transaction Date*
Used as the default ticket entry date. The default value is the working date.
Fields followed by the * character are mandatory.
- Enter the file to be imported in Filename.
- Enter the Transaction Date.
The Import Multiple Source check box is displayed only if the selected manufacturer is « Alkon ». This functionality is not available for other manufacturers. It allows you to import quarry tickets for many sources at the same time (in Ticket Management, the source is equivalent to a project).
For manufacturers « Alkon », the External Source column will also be displayed in the import grid.
- Click the Import File icon to load the selected file in the import grid.
Only fields that are not documented in section 8 are documented in this section.
Field
Description
Line
Ticket line number.
Message
Error message, if applicable.
Import
Used to import the ticket.
NOTES: If the box is checked, the system validates and imports the ticket.
If it detects that the ticket is already in the system, it automatically clears the box.
- Click the Validate the Table icon to ensure the integrity of the data to be imported.
The table must be checked if manual corrections are made to imported data.
- Click the Apply icon to import the data from the grid in maestro*.
- Confirm the information in the Details tab:
Field
Description
Counter
Counter number generated by maestro*.
Source
Source of the ticket; project.
Ticket No.
Delivery ticket number generated by the scale.
Ticket ID
Unique identification number on the ticket.
NOTE: This information is provided on import by Marcotte.
Date
Date the ticket was created.
NOTES: The system uses this date to calculate the discounts defined in the customer discount table.
This date is not necessarily the posting date.
User No.
Displays the user who entered the transaction.
Date Entered
Import date.
Quotation
Quotation number from the Concrete Bids option.
Trip No.
Trip number.
Truck Number
Truck number from Define Trucks.
NOTE: The truck number is always checked unless the system is configured otherwise in Configuration.
- Material section:
Field
Description
Status
Available values:
Entry
Lets you transfer the ticket to invoicing.
On Hold
Used to keep the ticket and untransferred transactions.
Non chargeable
Used to prevent invoicing of this section of the ticket.
To be validated
Used to note that the ticket must be checked before it is transferred.
Invoicing Type
Available values:
Internal
Used to generate an invoice for an internal customer or an existing project in Project Management.
Payable
Used to identify a ticket for which an invoice will be received from a supplier.
Receivable
Used to generate an invoice for an external customer.
COD Sale
Identifies a cash sale. In this case, the prices are from the ticket, not maestro*.
NOTE: This field can be used only if the Invoicing Type is set to Receivable.
RM Invoice
Invoice number available after invoicing.
Contract No
Customer’s contract number.
Name
Name of the customer to whom the ticket is invoiced.
Address
Shipping address.
Zip Code
ZIP or postal code.
Record
Customer code or supplier code according to the ticking billing type.
NOTE: For a receivable ticket, the customer code can be received as an External Code defined in Customer Management.
Description
Name of the customer or supplier linked to the Record field.
Work Order
This field is displayed only if the invoicing type is Internal. Select the work order from the work order file. The selection of a work order will display the project linked to it.
Company
If the Invoicing Type is set to Internal, it allows the specification of the default destination company.
Project
Project number or customer project number, if the Invoicing Type is Receivable.
NOTES: This field is used if the Define Internal Ticket field is set to 1 - Project in Configuration.
The project can affect grouping on the invoice. The group as defined in Configuration.
If the invoicing type is Internal, the project must be selected from the project file.
Activity
This field is displayed only if the invoicing type is Internal. Select the activity from the activity file.
Group
This field is displayed only if the invoicing type is Internal. Select the group from the group file.
P.O.
Customer’s order number or internal reference number.
NOTE: The Order Number is used if the system applies discounts defined in the customer discount table.
Customer P.O.
Customer order number.
NOTE: The Customer P.O. is used for grouping on the invoice.
Resistance
Identifies the mechanical resistance required for the mixture.
Stone
Quantity of stone.
Job ID
Project identification number.
NOTE: This information is provided on import or can be entered manually.
Product
Product code to be invoiced.
NOTE: This product must exist in Catalogue Management.
Volume
Quantity.
Unit Price
Unit price of the product.
NOTE: The price should be displayed automatically if the UP Product Source field is set to 1-Maestro in Configuration. If the price is not displayed, check whether a price is entered in Catalogue Management or Define Customer Pricing.
Amount
Total amount of the product.
Extra
Product code to be invoiced.
NOTE: This product must exist in Catalogue Management.
Quantity
Quantity delivered to the customer.
Unit Price
Unit price of the additive.
NOTE: The price should be displayed automatically if the UP Product Source field is set to 1-Maestro in Configuration. If the price is not displayed, check whether a price is entered in Catalogue Management or Define Customer Pricing.
Amount
Total amount for each additive.
Billing Date
Invoice date.
User No.
User number.
- Wait Time section:
Only fields that are not automatically populated are documented.
Field
Description
Use
Use of concrete from Define Usage.
- If information has been changed, click Save.
Create a ticket from a pending transaction
- Click on the Pending Transactions icon.
The selection grid, at the top of the screen, displays the Concrete Tickets’ pending transactions. - Select a pending transaction.
The pending transaction’s attached files are displayed in a new window.
If more than one file is attached, they will be displayed in the following order: PDF, Image, Excel, and Others.
- The system automatically completes some entries in the options window (the user who created the transaction, the date and time of creation, etc.).
Other entries will automatically be completed if the transaction comes from the Outlook add-in.
- Complete and save the transaction.
The transaction’s attached files will be available through the Document Management option upon saving.
See also